Systems and methods for controlling a geo-fence

ABSTRACT

The disclosure describes systems and methods for controlling a geo-fence. Through the use of the geo-fence and through monitoring of connections between mobile devices and the vehicle, a geo-fence is dynamically enabled and disabled for a user of a vehicle and the geo-fence control system provides notifications to users of the vehicle.

BACKGROUND

In the sharing economy or even within a group, such as a family, anumber of users may share the use of a vehicle. To make such sharingpossible, it is important to know when the vehicle is available. Inaddition, it is important to track the unauthorized use of the vehicle.It is with respect to these and other considerations that the disclosuremade herein is presented.

DESCRIPTION OF THE FIGURES

The detailed description is set forth with reference to the accompanyingdrawings. The use of the same reference numerals may indicate similar oridentical items. Various embodiments may utilize elements and/orcomponents other than those illustrated in the drawings, and someelements and/or components may not be present in various embodiments.Elements and/or components in the figures are not necessarily drawn toscale. Throughout this disclosure, depending on the context, singularand plural terminology may be used interchangeably.

FIG. 1 illustrates an example functional schematic of a geo-fencecontrol system including a vehicle, a mobile device, and a server inaccordance with the present disclosure.

FIG. 2 is a flow chart and schematic illustration of an example methodof creating a geo-fence account.

FIG. 3 is a flow chart and a schematic illustration of an example methodof providing a geo-fence.

FIG. 4 is a flow chart and a schematic illustration of an example methodof disabling a geo-fence.

FIG. 5 is a flow chart and a schematic illustration of an example methodof providing notifications to a mobile device associated with ageo-fence account.

FIG. 6 is a flow chart and a schematic illustration of an example methodof confirming possession of a vehicle by a user with a geo-fenceaccount.

DETAILED DESCRIPTION Overview

The disclosure provides systems and methods for controlling a geo-fence.In particular, a geo-fence is dynamically enabled and disabled for auser of a vehicle. Dynamically enabling and disabling the geo-fenceprovides that the user does not have to manually turn on and off thegeo-fence, which a user may forget to do.

Through the use of the geo-fence and through monitoring of connectionsbetween mobile devices and the vehicle, a last user of the vehicle canget notifications when another authorized user uses the vehicle and whenthe vehicle leaves an area of a geo-fence. The last user can alsoreceive notifications when an unconfirmed or unauthorized user haspossession of the vehicle and when the vehicle leaves the area of thegeo-fence. These notifications allow for more efficient sharing of thevehicle and for tracking the vehicle during unauthorized use.

According to one method, a vehicle stores a first mobile deviceidentifier that is based on a connection between a first mobile deviceand the vehicle and is marked as a last device connected to the vehicle.The geo-fence control system determines a vehicle location and accessesa geo-fence account associated with the first mobile device identifier.Based on a setting in the geo-fence account, the geo-fence controlsystem activates a geo-fence around the vehicle location.

Upon connection of a mobile device to the vehicle, the vehicledetermines a second mobile device identifier. The geo-fence controlsystems compares the first mobile device identifier to the second mobiledevice identifier. If the first mobile device identifier is the same asthe second mobile device identifier, the geo-fence control systemsdisables the geo-fence.

These and other advantages of the present disclosure are provided ingreater detail herein.

ILLUSTRATIVE EMBODIMENTS

The disclosure will be described more fully hereinafter with referenceto the accompanying drawings, in which exemplary embodiments of thedisclosure are shown, and not intended to be limiting.

FIG. 1 illustrates a vehicle 10, a mobile device 20, and a server 40 incommunication with one another. Although illustrated as a car, thevehicle may take the form of another passenger or commercial automobilesuch as, for example, a truck, a sport utility, a crossover vehicle, avan, a minivan, a taxi, a bus, etc., and may be configured to includevarious types of automotive drive systems. Example drive systems caninclude various types of internal combustion engine (ICE) powertrainshaving a gasoline, diesel, or natural gas-powered combustion engine withconventional drive components such as, a transmission, a drive shaft, adifferential, etc.

In another configuration, the vehicle 10 may be configured as anelectric vehicle (EV). More particularly, the vehicle 10 may include abattery EV (BEV) drive system. The vehicle 10 may be configured as ahybrid EV (HEV) having an independent onboard power plant or a plug-inHEV (PHEV) that includes a HEV powertrain connectable to an externalpower source (including a parallel or series hybrid powertrain having acombustion engine power plant and one or more EV drive systems). HEVscan include battery and/or super capacitor banks for power storage,flywheel power storage systems, or other power generation and storageinfrastructure.

The vehicle 10 may be further configured as a fuel cell vehicle (FCV)that converts liquid or solid fuel to usable power using a fuel cell,(e.g., a hydrogen fuel cell vehicle (HFCV) powertrain, etc.) and/or anycombination of these drive systems and components.

Further, the vehicle 10 may be a manually driven vehicle, and/or beconfigured to operate in a fully autonomous (e.g., driverless) mode(e.g., level-5 autonomy) or in one or more partial autonomy modes.Examples of partial autonomy modes are widely understood in the art asautonomy Levels 1 through 5.

The mobile device 20 includes a processor 22 and a memory 24. The memory24 stores a mobile device application 26 including program instructionsthat, when executed by the processor 22, performs aspects of thedisclosed methods described below including setting up a geo-fenceaccount, receiving notifications, and sending confirmations. As such,the mobile device 20 and mobile device application 26 may be part a of ageo-fence control system 100 described in further detail below includingtransmitting information for such systems.

The server 40 (e.g., one or more servers) may be part of a cloud-basedcomputing infrastructure, and may be associated with and/or include aTelematics Service Delivery Network (SDN) that provides digital dataservices to the vehicle 10. The server 40 includes a processor 42 and amemory 44. The memory 44 includes a server application 46 includingprogram instructions that, when executed by the processor 42, preformsaspects of the disclosed methods including controlling a geo-fence andsending and receiving notifications and information. For example, theserver application 46 generates and accesses a geo-fence account list 48and sends notifications to mobile devices 20 on the geo-fence accountlist 48. As such, the server 40 and server application 46 may be part ofthe geo-fence control system 100 described in further detail below ormay transmit information for such systems.

The vehicle 10 includes an automotive computer 30. The automotivecomputer 30 includes a processor 32 and a memory 34. The memory 34includes a vehicle application 36 including program instructions that,when executed by the processor 32, preforms aspects of the disclosedmethods including gathering, sending, and receiving information. Forexample, the vehicle application 36 generates and accesses a list ofdevices 38; gathers information from vehicle systems including a vehiclelocation 73, “on” and “off” states 314, 316 of the vehicle 10, andinstances of pairing 222 the vehicle 10 to a mobile device 20; and sendsinformation to the server 40 as described in further detail below. Assuch, the automotive computer 30 and vehicle application 36 may be parta of the geo-fence control system 100 described in further detail belowor may transmit information for such systems.

The memory 24, 34, 44 may be a non-transitory computer-readable memorystoring program code. The memory can include any one or a combination ofvolatile memory elements (e.g., dynamic random access memory (DRAM),synchronous dynamic random access memory (SDRAM), etc.) and can includeany one or more nonvolatile memory elements (e.g., erasable programmableread-only memory (EPROM), flash memory, electronically erasableprogrammable read-only memory (EEPROM), programmable read-only memory(PROM), etc.

The vehicle 10 further includes a Vehicle Controls Unit (VCU) 50. TheVCU 50 includes a plurality of electronic control units (ECUs) 52disposed in communication with the automotive computer 30. Theautomotive computer 30 may be or include an electronic vehiclecontroller. The automotive computer 30 and the VCU 50 may be installedin an engine compartment of the vehicle 10 (as schematicallyillustrated) or elsewhere in the vehicle 10.

The ECUs 52 may control aspects of vehicle operation and communicationusing inputs from human drivers, inputs from a vehicle systemcontrollers, and/or via wireless signal inputs received via wirelesschannel(s) from other connected devices such as a mobile device, amongothers. The ECUs 52 (e.g., when configured as nodes in a CAN bus 80described in further detail below) may each include a central processingunit (CPU), a CAN controller, and/or a transceiver (not shown in FIG.1).

The VCU 50 may coordinate the sharing of data between vehicle systems,connected servers (e.g., server 40) and devices (e.g., mobile device20). The VCU 50 can include or communicate with any combination of theECUs 52, such as, for example, a Body Control Module (BCM) 60, an EngineControl Module (ECM) 62, a Transmission Control Module (TCM) 64, aTelematics Control Unit (TCU) 66, a Restraint Control Module (RCM) 68,and the like. The ECUs 52 described with respect to the VCU 50 areprovided for exemplary purposes only, and are not intended to belimiting or exclusive. Control and/or communication with other controlmodules not shown in FIG. 1 is possible, and such control iscontemplated.

The ECUs 52 can communicate with one another and the automotive computer30 by way of a Controller Area Network (CAN) bus 80. Accordingly, theautomotive computer 30 may retrieve information from, send informationto, and otherwise interact with the ECUs 52 to perform steps describedaccording to embodiments of the present disclosure.

The CAN bus 80 may be configured as a multi-master serial bus standardfor connecting two or more of the ECUs 52 as nodes using a message-basedprotocol that can be configured and/or programmed to allow the ECUs 52to communicate with each other. The CAN bus 80 may be or include a highspeed CAN (which may have bit speeds up to 1 Mb/s on CAN, 5 Mb/s on CANFlexible Data Rate (CAN FD)), and can include a low-speed or faulttolerant CAN (up to 125 Kbps), which may, in some configurations, use alinear bus configuration.

The CAN bus 80 may connect CAN bus nodes (e.g., the ECUs 52) to eachother through a two-wire bus, which may be a twisted pair having anominal characteristic impedance. The CAN bus 80 may also beaccomplished using other communication protocol solutions, such as MediaOriented Systems Transport (MOST) or Ethernet. In other aspects, the CANbus 80 may be a wireless intra-vehicle CAN bus.

ECUs 52 are now described in further detail.

The BCM 60 generally includes an integration of sensors, vehicleperformance indicators, and variable reactors associated with vehiclesystems. The BCM 60 may include processor-based power distributioncircuitry that can control functions associated with the vehicle bodysuch as lights, windows, security, door locks and access control, andvarious comfort controls. The BCM 60 may also operate as a gateway forbus and network interfaces to interact with remote ECUs (not shown inFIG. 1).

The BCM 60 may coordinate any one or more functions from a wide range ofvehicle functionality, including energy management systems, alarms,vehicle immobilizers, ignition systems, driver and rider accessauthorization systems, Phone-as-a-Key (PaaK) systems, driver assistancesystems, Autonomous Vehicle (AV) control systems, power windows, doors,actuators, and other functionality, etc. The BCM 60 may be configuredfor vehicle energy management, exterior lighting control, wiperfunctionality, power window and door functionality, heating ventilationand air conditioning systems, and driver integration systems. In otheraspects, the BCM 60 may control auxiliary equipment functionality,and/or is responsible for integration of such functionality. In oneaspect, a geo-fence control system 100 may integrate the system using,at least in part, the BCM 60.

The mobile device application 26 may communicate with the BCM 60 toprovide a phone-as-a-key (PAAK) system. The mobile device application 26may use a digital key over a connection via the TCU 66. In particular,if the mobile device 20 is in-range (e.g., nearfield communication) andconnected to the vehicle 10, the mobile device application 26 provides adigital key to the BCM 60, and the BCM 60 enables control of doorlock/unlock systems and start/stop ignition systems via vehicle userinputs.

The TCU 66 can be configured to provide vehicle connectivity to wirelesscomputing systems onboard and offboard the vehicle 10 and isconfigurable for wireless communication between the vehicle 10 and othersystems, computers, and modules. For example, the TCU 66 includes aNavigation (NAV) system 70 for receiving and processing a GPS signalfrom a GPS 72, a Bluetooth® Low-Energy Module (BLEM) 74, a Wi-Fitransceiver, an Ultra-Wide Band (UWB) transceiver, and/or other wirelesstransceivers (not shown in FIG. 1).

The NAV system 70 is configured and/or programmed to determine aposition of the vehicle 10. The NAV system 70 includes a GlobalPositioning System (GPS) receiver configured or programmed totriangulate a position or vehicle location 73 of the vehicle 10 relativeto satellites or terrestrial based transmitter towers associated withthe GPS 72. The NAV system 70, therefore, is configured or programmedfor wireless communication.

The NAV system 70 may be further configured or programmed to developroutes from a current vehicle location 73 to a selected destination, aswell as display a map and present driving directions to the selecteddestination. In some instances, the NAV system 70 may develop the routeaccording to a user preference. Examples of user preferences may includemaximizing fuel efficiency, reducing travel time, travelling theshortest distance, or the like.

NAV system 70 is configured to measure and collect tracking dataincluding determine vehicle location 73, heading, speed, acceleration,braking, and the like.

In addition, the TCU 66 generally includes wireless transmission andcommunication hardware that may be disposed in communication with one ormore transceivers associated with telecommunications towers and otherwireless telecommunications infrastructure. For example, the BLEM 74 isconfigured and/or programmed to receive messages from, and transmitmessages to, one or more cellular towers associated with atelecommunication provider, and/or and a Telematics Service DeliveryNetwork (SDN) associated with the vehicle 10 for coordinating vehiclefleet (not shown in FIG. 1).

The BLEM 74 may establish wireless communication using Bluetooth® andBluetooth Low-Energy® communication protocols by broadcasting and/orlistening for broadcasts of small advertising packets, and establishingconnections with responsive devices that are configured according toembodiments described herein. For example, the BLEM 74 may includeGeneric Attribute Profile (GATT) device connectivity for client devicesthat respond to or initiate GATT commands and requests, and connectdirectly with a mobile device 20.

The mobile device 20 and a server 40 can connect to the vehicle 10according to systems and methods described above. The mobile device 20and the server 40 also connect to one another through variouscommunication channels.

The mobile device 20 may connect with the vehicle 10 using wired and/orwireless communication protocols and transceivers. The mobile device 20may be communicatively coupled with the vehicle 10 via one or morenetwork(s) 92, which may communicate via one or more wireless channel(s)90, and/or may connect with the vehicle 10 directly (e.g., channel 94)using near field communication (NFC) protocols, Bluetooth® protocols,Wi-Fi, Ultra-Wide Band (UWB), and other possible data connection andsharing techniques. The vehicle 10 also receives and/or is incommunication with the Global Positioning System (GPS) 72.

In some aspects, the mobile device 20 may communicate with the vehicle10 through the one or more wireless channel(s) 90, which may beencrypted and established between the mobile device 20 and theTelematics Control Unit (TCU) 66. The mobile device 20 may communicatewith the TCU 66 using a wireless transmitter associated with the TCU 66on the vehicle 10. The transmitter may communicate with the mobiledevice 20 using a wireless communication network such as, for example,the one or more network(s) 92.

The mobile device 20 and the server 40 may be in direct communicationvia the wireless channel(s) 90 connected by the one or more network(s)92, and also in indirect communication (e.g., channel 94) via thevehicle 10.

The network(s) 92 illustrate an example of an example communicationinfrastructure in which the connected devices discussed in variousembodiments of this disclosure may communicate. The network(s) 92 may beand/or include the Internet, a private network, public network or otherconfiguration that operates using any one or more known communicationprotocols such as, for example, transmission control protocol/Internetprotocol (TCP/IP), Bluetooth®, Wi-Fi based on the Institute ofElectrical and Electronics Engineers (IEEE) standard 802.11, Ultra-WideBand (UWB), and cellular technologies such as Time Division MultipleAccess (TDMA), Code Division Multiple Access (CDMA), High Speed PacketAccess (HSPDA), Long-Term Evolution (LTE), Global System for MobileCommunications (GSM), and Fifth Generation (5G), to name a few examples.

FIG. 1 illustrates an example functional schematic of a geo-fencecontrol system 100 including some elements described above. Thegeo-fence control system 100 can include the mobile device 20 includingthe mobile device application 26, the server 40 including the serverapplication 46 and the geo-fence account list 48, and the vehicle 10including the vehicle application 36 and the list of devices 38. Thegeo-fence control system 100 also includes vehicle sensors and systemsfor determining connection of a mobile device 20 to the vehicle 10 andthe vehicle location 73.

Referring to FIG. 2, the vehicle application 36 generates the list ofdevices 38 and stores the list of devices 38 in the memory 34. The listof devices 38 is a list of devices (e.g., including mobile device 20)that have paired 222 to or established a connection with the vehicle 10.For example, the mobile device 20 may be paired 222 with the vehicle 10through the BLEM 74 or through the BCM 60 (e.g., using a PAAK system).The vehicle application 36 monitors devices that pair 222 with thevehicle 10 and adds a mobile device identifier 224 to the list ofdevices 38 for mobile devices 20 that pair 222 with the vehicle 10.

The vehicle application 36 further marks 312 which of the mobile deviceidentifiers 224 in the list of devices 38 was the last to connect to thevehicle 10. In FIG. 3, a last connected mobile device identifier 224 ismarked 312 in the list of devices 38. For example, the vehicleapplication 36 marks 312 the mobile device identifier 224 of the lastconnected mobile device upon disconnection of the mobile device 20 fromthe vehicle 10.

Referring to FIG. 2, a setup method 200 for a geo-fence account 242 isnow described in further detail. The geo-fence account 242 is added thegeo-fence account list 48. According to a first step 210, the mobiledevice application 26 receives a selection of a dynamic geo-fencesetting 212, for example, via an interface of the mobile device 20.

According to a second step 220, the mobile device application 26 and/orthe vehicle application 36 determines if the mobile device 20 has beenpaired 222 to the vehicle 10. For example, the mobile device 20 may bepaired 222 with the vehicle 10 as described above using a Bluetooth LowEnergy (BLE) vehicle interface or a phone-as-a-key (PAAK) vehicleinterface. If the mobile device 20 has been paired 222 to the vehicle10, a corresponding mobile device identifier 224 (e.g., a name or numberassociated with the mobile device 20) shows up in the list of devices38. Accordingly, step 220 can include a request from the mobile device20 to the vehicle 10 to confirm that the mobile device identifier 224 ofthe mobile device 20 is in the list of devices 38.

According to a third step 230, if the mobile device 20 has been paired222 to the vehicle 10 (i.e., the mobile device identifier 224 is foundin the list of devices 38), the mobile device application 26 determinesif the vehicle 10 received account information 232 from the mobiledevice 20 and that the account is verified 234 (e.g., through anotification to the mobile device 20 via the mobile device application26, an email, a text, using the account information 232). For example,the account information 232 includes contact information fornotifications such as a phone number or email address.

According to a fourth step 240, if the vehicle 10 received accountinformation 232 and the account is verified 234, the vehicle 10 providesthe mobile device identifier 224 of the mobile device 20 and the accountinformation 232 to the server 40. The server 40 adds a geo-fence account242 to the geo-fence account list 48. The geo-fence account 242 includesthe mobile device identifier 224 of the mobile device 20, the accountinformation 232, and a geo-fence setting 244 (e.g., on or off). Thegeo-fence setting 244 is controlled by and reflects the dynamicgeo-fence setting 212 in the mobile device application 26 of the mobiledevice 20. A change in the dynamic geo-fence setting 212 via the mobiledevice application 26 causes the mobile device 20 to communicate thechange to the server 40 and the server 40 updates the geo-fence accountlist 48 based on the communicated change.

If the mobile device 20 was not paired, if account information was notreceived, or if the account is not verified, the method 200 returns tothe second step 220 to again pair 222 the mobile device 20 and thevehicle 10.

The server application 46 is now described in further detail. Referringto FIG. 3, the server application 46 is configured to set a geo-fence302 based on a vehicle location 73 and the geo-fence setting 244, and todeactivate the geo-fence 302 and/or notify users based on informationreceived from the vehicle 10 as described in further detail in themethods below.

The geo-fence 302 includes a geo-fence perimeter 304 (e.g., a virtualperimeter) around the vehicle location 73. The geo-fence perimeter 304may be defined by a radius and/or with respect to features of areal-world geographic area on a map.

The server application 46 monitors the vehicle location 73 with respectto the geo-fence perimeter 304. If the vehicle location 73 crosses thegeo-fence perimeter 304 to leave an area defined by the geo-fenceperimeter 304, a response by the server application 46 is triggered asdescribed in further detail below.

Referring to FIG. 3, a method 300 of setting a geo-fence 302 isdescribed. According to a first step 310, at a time t1, the vehicle 10transitions from an “off” state 314 to an “on” state 316. The state 314,316 of the vehicle 10 may be monitored, for example, by the BCM 60.

According to a second step 320, the mobile device 20 is paired 222 tothe vehicle 10. As the mobile device 10 has previously been paired 222to the vehicle 10 (e.g., at least during setup of the geo-fence account242), the mobile device identifier 224 of the mobile device 20 shows upin the list of devices 38.

According to a third step 330, at a time t2, the vehicle 10 determinesan indicator 332 of an end of use of the vehicle 10. For example, theindicator 332 can include a transition from the “on” state 316 to the“off” state 314, use of a PAAK (the mobile device 20) to initiate such atransition, ignition set to the “off” state 314, opening of a door withthe ignition set to the “off” state 314, unpairing or disconnecting themobile device 20 from the vehicle 10, combinations thereof, and thelike.

According to a fourth step 340, upon determining the indicator 332, themobile device identifier 224 of the mobile device 20 is marked 312 asthe last connected mobile device in the list of devices 38.

According to a fifth step 350, upon determining the indicator 332, thevehicle 10 sends the mobile device identifier 224 of the mobile device20 that is marked 312 as the last connected mobile device to the server40. The server 40 determines if the geo-fence account 242 for the mobiledevice identifier 224 in the account list 48 has the geo-fence setting244 set to “on.”

According to a sixth step 360, if the geo-fence setting 244 is set to“on,” the server 40 requests or receives a vehicle location 73 from thevehicle 10 (e.g., from the NAV system 70) and collects or requestsadditional information. For example, the additional information mayinclude statistics for the vehicle location 73 (e.g., crime statistics)or account information 232 in the geo-fence account 242 such as amaximum walking distance set by a user of the mobile device 20.

According to a seventh step 370, the server 40 determines a geo-fenceperimeter 304 around the vehicle location 73. The geo-fence perimeter304 or area of the geo-fence 302 may be defined by additionalinformation describe above. For example, if the crime statistics areabove-average at the vehicle location 73, the geo-fence perimeter 304 issmaller (e.g., a smaller radius) such that notifications will be sentsooner if the vehicle location 73 moves outside the geo-fence perimeter304.

As another example, the geo-fence perimeter 304 may be defined by themaximum distance a user of the mobile device 20 is willing to walk,which may be stored in the geo-fence account 242 associated with themobile device 20. Here, a first notification may be sent from the server40 to the mobile device 20 (i.e., with the mobile device identifier 224that is marked 312 as the last connected mobile device) if the vehicle10 has been moved or possessed by another user (e.g., another mobiledevice) but the vehicle 10 has not crossed the geo-fence perimeter 304.The user of the last connected mobile device 312 may be willing to walkto the new vehicle location 73 within the geo-fence perimeter 304 toretake possession. A second notification may be sent if the vehicle 10has crossed the geo-fence perimeter 304 so that the user knows thevehicle 10 is not within walking distance and to find another form oftransportation if necessary.

Referring to FIG. 4, a method 400 of deactivating the geo-fence 302 isdescribed. Here, the user with the mobile device 20 (i.e., with themobile device identifier 224 that is marked 312 as the last connectedmobile device) returns to the vehicle 10. According to a first step 410,the vehicle 10 transitions from an “off” state 314 to an “on” state 316.According to a second step 420, the mobile device 20 is paired 222 tothe vehicle 10. According to a third step 430, the vehicle 10 comparesthe mobile device identifier 224 of the paired 222 mobile device 20 tomobile device identifier 224 that is marked 312 as the last connectedmobile device in the list of devices 38. According to a fourth step 440,if the mobile device identifier 224 of the paired 222 mobile device 20matches the mobile device identifier 224 that is marked 312 as the lastconnected mobile device in the list of devices 38, the vehicleapplication 36 signals the server 40 and the server 40 deactivates thegeo-fence 302 via the server application 46.

Referring to FIG. 5, a method 500 of receiving notifications by themobile device 20 (i.e., with the mobile device identifier 224 that ismarked 312 as the last connected mobile device) is described. Here, auser with a mobile device 20 that is not marked 312 as the lastconnected mobile device takes possession of the vehicle 10.

According to a first step 510, the vehicle 10 transitions from an “off”state 314 to an “on” state 316. According to a second step 520, themobile device 20 is paired 222 to the vehicle 10.

According to a third step 530, the mobile device identifier 224 of themobile device 20 is compared to the mobile device identifier 224 that ismarked 312 as the last connected mobile device in the list of devices38. According to a fourth step 540, if the mobile device identifier 224of the mobile device 20 does not match the mobile device identifier 224that is marked 312 as the last connected mobile device in the list ofdevices 38, the mobile device identifier 224 of the mobile device 20 iscompared to the other mobile device identifiers 224 in the list ofdevices 38.

According to a fifth step 550, if the mobile device identifier 224matches one of the other mobile device identifiers 224 in the list ofdevices 38, the vehicle application 36 provides the server 40 with themobile device identifier 224 that is marked 312 as the last connectedmobile device and an indication that the vehicle 10 is paired 222 to amobile device 20 in the list of devices 38 other than the last connectedmobile device.

According to a sixth step 560, in response, the server 40 provides afirst notification to the mobile device 20 with the mobile deviceidentifier 224 that is marked 312 as the last connected mobile device.The first notification indicates that the vehicle 10 is in possession bya user associated with a mobile device identifier 224 in the list ofdevices 38.

The server 40 uses the account information 232 in the geo-fence account242 in the geo-fence account list 48 to communicate with the mobiledevice 20 with the mobile device identifier 224 that is marked 312 asthe last connected mobile device. For example, the mobile device 20 isnotified via a text message or via the mobile device application 26 onthe mobile device 20.

According to a seventh step 570, if the vehicle location 73 is outsidethe geo-fence perimeter 304, the server 40 provides a secondnotification to the mobile device 20 with the mobile device identifier224 that is marked 312 as the last connected mobile device. The secondnotification indicates that the vehicle 10 is outside the geo-fenceperimeter 304.

Referring to FIG. 6, a method 600 of confirming possession or trackingunconfirmed possession is described. Here, a user takes possession ofthe vehicle 10 without pairing 222 a mobile device 20 to the vehicle 10.

According to a first step 610, the vehicle 10 transitions from an “off”state 314 to an “on” state 316. According to a second step 620, thevehicle 10 determines that a mobile device 20 is not paired to thevehicle 10. For example, a user starts the ignition with a physical keyand has a mobile device 20 that fails to pair to the vehicle 10.

According to a third step 630, the vehicle 10 (e.g., the vehicleapplication 36) notifies the server 40 that the vehicle is in the “on”state 316 and a mobile device is not paired to the vehicle 10.

According to a fourth step 640, in response to the notification from thevehicle 10, the server 40 notifies mobile devices 20 with associatedwith geo-fence accounts 242 (e.g., those with mobile device identifiers224) in the geo-fence account list 48 with the geo-fence setting 244 setto “on.”

The server 40 uses the account information 232 in the geo-fence accounts242 to communicate with the mobile devices 20. For example, the mobiledevice 20 with the mobile device identifier 224 that is marked 312 asthe last connected mobile device is notified via a text message or viathe mobile device application 26 on the mobile device 20. Thenotification to the mobile devices 20 includes a request forconfirmation of possession of the vehicle 10.

In addition, the server 40 begins receiving tracking information, forexample, from the NAV system 70 of the vehicle 10. The trackinginformation includes (or can be used to determine) location, heading,speed, acceleration, braking, and the like.

According to a fifth step 650, if the server 40 receives a confirmation652 from one of the mobile devices 20 to which the notification wassent, the server 40 may cease collection of tracking information anddetermine whether the response is from a mobile device 20 with a mobiledevice identifier 224 that is marked 312 as the last connected mobiledevice. If the one of the mobile devices 20 has the mobile deviceidentifier 224 that is marked 312 as the last connected mobile device,the server 40 may deactivate the geo-fence 302 (e.g., similar to method400). If the one of the mobile devices 20 has a mobile device identifier224 that is not marked 312 as the last connected mobile device, themethod 600 may proceed according to notification steps 560, 570 ofmethod 500.

According to a sixth step 660, if the server 40 does not receiveconfirmation from one of the mobile devices 20 to which the notificationwas sent, and if the geo-fence perimeter 304 is crossed, the server 40sends a notification to the mobile device 20 with the mobile deviceidentifier that is the last connected mobile device 312.

In the above disclosure, reference has been made to the accompanyingdrawings, which form a part hereof, which illustrate specificimplementations in which the present disclosure may be practiced. It isunderstood that other implementations may be utilized, and structuralchanges may be made without departing from the scope of the presentdisclosure. References in the specification to “one embodiment,” “anembodiment,” “an example embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may not necessarily include theparticular feature, structure, or characteristic. Moreover, such phrasesare not necessarily referring to the same embodiment. Further, when afeature, structure, or characteristic is described in connection with anembodiment, one skilled in the art will recognize such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described.

It should also be understood that the word “example” as used herein isintended to be non-exclusionary and non-limiting in nature. Moreparticularly, the word “exemplary” as used herein indicates one amongseveral examples, and it should be understood that no undue emphasis orpreference is being directed to the particular example being described.

A computer-readable medium (also referred to as a processor-readablemedium) includes any non-transitory (e.g., tangible) medium thatparticipates in providing data (e.g., instructions) that may be read bya computer (e.g., by a processor of a computer). Such a medium may takemany forms, including, but not limited to, nonvolatile media andvolatile media. Computing devices may include computer-executableinstructions, where the instructions may be executable by one or morecomputing devices such as those listed above and stored on acomputer-readable medium.

With regard to the processes, systems, methods, heuristics, etc.described herein, it should be understood that, although the steps ofsuch processes, etc. have been described as occurring according to acertain ordered sequence, such processes could be practiced with thedescribed steps performed in an order other than the order describedherein. It further should be understood that certain steps could beperformed simultaneously, that other steps could be added, or thatcertain steps described herein could be omitted. In other words, thedescriptions of processes herein are provided for the purpose ofillustrating various embodiments and should in no way be construed so asto limit the claims.

Accordingly, it is to be understood that the above description isintended to be illustrative and not restrictive. Many embodiments andapplications other than the examples provided would be apparent uponreading the above description. The scope should be determined, not withreference to the above description, but should instead be determinedwith reference to the appended claims, along with the full scope ofequivalents to which such claims are entitled. It is anticipated andintended that future developments will occur in the technologiesdiscussed herein, and that the disclosed systems and methods will beincorporated into such future embodiments. In sum, it should beunderstood that the application is capable of modification andvariation.

All terms used in the claims are intended to be given their ordinarymeanings as understood by those knowledgeable in the technologiesdescribed herein unless an explicit indication to the contrary is madeherein. In particular, use of the singular articles such as “a,” “the,”“said,” etc. should be read to recite one or more of the indicatedelements unless a claim recites an explicit limitation to the contrary.Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments could include, while other embodiments may not include,certain features, elements, and/or steps. Thus, such conditionallanguage is not generally intended to imply that features, elements,and/or steps are in any way required for one or more embodiments.

What is claimed is:
 1. A method, comprising: storing, by a vehicle, afirst mobile device identifier, wherein the first mobile deviceidentifier is based on a connection between a first mobile device andthe vehicle, wherein the first mobile device identifier is marked as alast device connected to the vehicle; determining a vehicle location ofthe vehicle; accessing a geo-fence account associated with the firstmobile device identifier; activating, based on a setting of thegeo-fence account, a geo-fence based on the vehicle location;determining, upon connection of a second mobile device to the vehicle, asecond mobile device identifier; comparing the first mobile deviceidentifier to the second mobile device identifier; and disabling thegeo-fence based on the first mobile device identifier being identical tothe second mobile device identifier.
 2. The method of claim 1, furthercomprising receiving an indication of an end of use of the vehicle. 3.The method of claim 2, wherein marking the first mobile deviceidentifier as the last device connected to the vehicle is based on theindication of an end of use of the vehicle.
 4. The method of claim 2,wherein the vehicle location is based on the indication of an end of useof the vehicle.
 5. The method of claim 1, wherein the second mobiledevice identifier corresponds to an indicator of a beginning of use ofthe vehicle.
 6. The method of claim 1, further comprising generating alist of mobile device identifiers corresponding to mobile devices thathave connected to the vehicle.
 7. The method of claim 1, furthercomprising comparing the second mobile device identifier to a list ofmobile device identifiers, wherein the list of mobile device identifiersidentify mobile devices that have connected to the vehicle.
 8. Themethod of claim 7, further comprising sending a message to the firstmobile device based on the second mobile device identifier beingidentical to one of the list of mobile device identifiers other than thefirst mobile device identifier.
 9. The method of claim 8, furthercomprising sending a message to the first mobile device based on thevehicle location crossing a virtual perimeter of the geo-fence.
 10. Themethod of claim 7, further comprising collecting vehicle tracking databased on the second mobile device identifier not being identical to anyof the list of mobile device identifiers.
 11. The method of claim 7,further comprising sending a possession confirmation message to mobiledevices associated with an account in a list of geo-fence accounts. 12.The method of claim 11, wherein the possession confirmation messageincludes a request to confirm whether a user one of the mobile devicesis in current possession of the vehicle.
 13. The method of claim 11,further comprising deactivating the geo-fence if a response from thefirst mobile device confirms possession of the vehicle.
 14. The methodof claim 11, further comprising sending a message to the first mobiledevice if a response from a mobile device associated with an account inthe list of geo-fence accounts, other than the first mobile device,confirms possession of the vehicle.
 15. The method of claim 14, furthercomprising sending a message to the first mobile device if a vehiclelocation crosses a virtual perimeter of the geo-fence.
 16. The method ofclaim 11, further comprising sending a message to the first mobiledevice if a response to the possession confirmation message is notreceived.
 17. The method of claim 1, further comprising controlling thesetting of the geo-fence account with an application of a mobile device.18. A geo-fence control system, comprising: a vehicle, comprising: aprocessor; a memory, comprising: a list of mobile device identifierscorresponding to mobile devices that have connected to the vehicle,wherein one of the mobile device identifiers is marked as a last mobiledevice connected to the vehicle; and a vehicle application comprisinginstructions that, when executed by the processor, causes the vehicleto: determine a mobile device identifier of a currently connected mobiledevice; and a navigation system configured to determine a vehiclelocation of the vehicle; a server, comprising: a processor; a memory,comprising: a list of a geo-fence accounts, each geo-fence accountincluding a mobile device identifier and a geo-fence setting, wherein atleast one of the geo-fence accounts includes the one of the mobiledevice identifiers; a geo-fence application comprising instructionsthat, when executed by the processor, causes the server to: activate,based on a geo-fence setting of a geo-fence account, a geo-fence basedon the vehicle location; and disable the geo-fence if the mobile deviceidentifier of the currently connected mobile device is the same as theone of the mobile device identifiers marked as the last mobile deviceconnected to the vehicle.
 19. The geo-fence control system of claim 18,wherein the geo-fence application comprises instructions that, whenexecuted by the processor, cause the server to send a notification tothe last mobile device connected to the vehicle if the mobile deviceidentifier is the same as one of the list of mobile device identifiersother than the mobile device identifier marked as the last mobile deviceconnected to the vehicle.
 20. The geo-fence control system of claim 19,wherein the geo-fence application comprises instructions that, whenexecuted by the processor, cause the server to send a notification tothe last mobile device connected to the vehicle if the vehicle locationcrosses the geo-fence.